docs: add Hermes issue triage example - #539
Conversation
|
Thanks @918154429 for contributing a tool example — visible, reviewable PRs like this grow the reference for everyone. What happens next
More ways to help — loop-engineering maintainers |
|
Thanks @918154429 — this is a scoped docs/example PR (Hermes issue-triage + index links) and it stays in the week-one propose-only boundary, matching the existing Hermes examples. Not merging yet: required checks validate and audit are |
cobusgreyling
left a comment
cobusgreyling
left a comment
There was a problem hiding this comment.
Looks good — fills the empty Hermes Issue Triage matrix cell and stays in week-one propose-only (--deliver local, no issue writes, duplicates/human-owned items escalate). Matches the existing Hermes daily-triage / pr-babysitter shape (cron + skill + state file). Validate and audit are green after first-time-contributor workflow approval. Merging.
2 participants
Summary
hermes cron--deliver localWhy
Hermes currently has Daily Triage, PR Babysitter, and CI Sweeper examples, but the Issue Triage matrix entry is still empty. This adds the missing L1 bridge while preserving the shared state schema and human safety gates.
Impact
Hermes users get a documented issue-triage starting point without granting repository write access. The example keeps issue changes human-owned during calibration and limits a later L2 to verifier-approved, allowlisted labels.
Validation
npm run validate:registrynpm run check:loop-initgit diff --check origin/main...HEADRefs #388